Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FE: Adding Schema (Value) and Schema (Key) tab to the Topic details view #4020

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

steffen-karlsson
Copy link

The two tabs will allow for quick access to the schemas for the messages produced to the topic.

Meaningful debug message is shown if schema is not available for either topic key or topic value and hasSchemaRegistryConfigured is true.

Tabs are not shown if hasSchemaRegistryConfigured is not true.

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

  • No need to
  • Manually (please, describe, if necessary)
  • Unit checks
  • Integration checks
  • Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
  • My changes generate no new warnings (e.g. Sonar is happy)
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged

tiny-white-kitten-873941684-2000-0bac130389984aba9751de5e5e50d25f

The two tabs will allow for quick access to the schemas for the messages produced to the topic.

Meaningful debug message is shown if schema is not available for either topic key or topic value and hasSchemaRegistryConfigured is true.

Tabs are not shown if hasSchemaRegistryConfigured is not true.
@steffen-karlsson steffen-karlsson requested a review from a team as a code owner July 7, 2023 12:51
getAreSchemaLatestRejected,
SCHEMA_LATEST_FETCH_ACTION,
} from 'redux/reducers/schemas/schemasSlice';
import LatestVersionItem from '../../../Schemas/Details/LatestVersion/LatestVersionItem';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we please use absolute path here instead of an relative path ?

cause that way it will not cause any issues if we displaced the component that this Schema uses.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, no worries let me fix that, when I'm home from vacation at my computer with this code 😊

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Mgrdich let's chill with the review, we might not need it, as I asked to raise a PR for an example, since we wanted to achieve something similar but not that similar :))

@Haarolean Haarolean marked this pull request as draft July 13, 2023 15:04
@Haarolean Haarolean self-assigned this Aug 3, 2023
@Haarolean Haarolean removed their assignment Sep 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants